home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000217-20000824
/
000009_news@columbia.edu _Thu Feb 17 17:10:04 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-08-23
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id RAA08149
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 17 Feb 2000 17:10:04 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id QAA24316
for kermit.misc@watsun.cc.columbia.edu; Thu, 17 Feb 2000 16:57:28 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Subject: Re: TELNET error with K95 1.19
Date: 17 Feb 2000 21:57:26 GMT
Organization: Columbia University
Message-ID: <88hqs6$nno$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <88hogo$mbo$1@nntp1.atl.mindspring.net>,
Bob Rodriguez <robertr@netcom17.netcom.com> wrote:
: The new TELNET terminal negotiation options in version 1.19
: seems to have introduced a problem when telneting to special ports
: that are not Unix logins. There's a MUD that I was able to get to ok with
: 1.17 as candum.acc.umu.se 2001, but now it times out with the following
: errors:
:
: -
: ?Telnet Protocol Timeout - connection closed
: ?Telnet waiting for response to WILL TERMINAL-TYPE
: ?Telnet waiting for response to WILL NAWS
: ?Telnet waiting for response to WILL AUTHENTICATION
: ?Telnet waiting for response to WILL NEW-ENVIRONMENT
:
: If I turn Telnet negotiation off, I can get through alright, but then
: none of my commands are echoed to the terminal and the terminal is not
: set to VT100.
This is going to be a Frequently Asked Question in the next few weeks.
I advise everyone to please read the Telnet Reference" in the online
Kermit 95 Manual.
MUD servers fall into one of two categories:
. they are telnet servers that run on non-telnet ports that
do not properly implement the telnet protocol. All they do
is output a series of bytes at the beginning of a connection
to fake a telnet client into thinking it is talking to a
real telnet server. This is done instead of actually implementing
a telnet state machine that would respond negatively to each of
the above negotiations.
In this case, you need to disable the negotiations of the
above telnet negotiations:
SET TELOPT TERMINAL-TYPE REFUSE
SET TELOPT NAWS REFUSE
SET TELOPT AUTH REFUSE
SET TELOPT NEW-ENV REFUSE
or
SET HOST /CONNECT host port /NO-TELNET-INIT
. they are not telnet servers at all and do not support any
telnet negotiations
SET HOST /CONNECT host port /RAW-SOCKET
In C-Kermit 7.0 and Kermit 95 1.1.19, the TELNET command means "use
Telnet protocol" to make the connection. If the connection is not
using Telnet protocol, the SET HOST should be used instead.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025
http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org